Method and system for collecting and processing marketing data

ABSTRACT

A system and method for the collection of marketing data simultaneously captures at a point-of-sale all financial and non-financial data pertaining to a specific consumer transaction. An electronic invoice is constructed from the captured data and transmitted to a credit authorization location via a communication link necessarily established to transmit a credit authorization request for the transaction. The electronic invoice contains line item data for each item purchased as part of the transaction. The invoice is organized around the identification number of the payment vehicle employed by the customer to pay for the transaction, thus linking the purchasing information contained in the invoice to a particular consumer. The credit authorization location receives the transmitted electronic invoice and forwards the invoice to a data warehouse, which may be located in a location remote from the credit authorization location. The data warehouse comprises a plurality of related data structures for storing the received data. The related data structures facilitate simple and flexible analysis and searching of the collected market data.

FIELD OF THE INVENTION

[0001] The invention relates to a system and method for collecting andprocessing marketing data.

BACKGROUND OF THE INVENTION

[0002] Market research is an important business tool which permitsmanufacturers, retailers, financial institutions, and others tocost-effectively target their marketing and sales activities andefficiently reach potential customers. These organizations rely heavilyon market data in planning new products, sales strategies andpromotions, and when making a variety of other sales and marketingrelated business decisions.

[0003] In the past, marketing data has been collected in several ways.Typically, market research firms are employed to collect data usingsurveys, questionnaires, and other costly and time-consuming techniques.This information is then processed using statistical techniques in aneffort to extrapolate therefrom significant trends in consumer behavior.Although based on statistically significant correlations, thesetechniques cannot with absolute precision determine the buying patternsof particular population segments or individual consumers. Indeed, asrecognized in the art, such surveys often yield inaccurate andmisleading results.

[0004] In contrast, some organizations, particularly large retailers,collect marketing data by tracking sales transactions at the retailers'points of sale. This technique, however, provides only crude data suchas the number and types of items sold by the merchant. It does notprovide detailed data regarding sales patterns of particularsocioeconomic groups or individual customers.

[0005] To collect more precise data, retailers sometimes providecustomers with “preferred customer” cards or the like. The “preferredcustomer” card typically comprises a customer identification numberlinked to a database record which stores information relating to thecustomer's past purchases. Each time the customer makes a purchase, themerchant scans or manually enters the customer identification numberfrom the “preferred customer” card into the merchant's point of sale(POS) computer. The merchant then scans or manually enters theidentification codes of the items purchased by the customer. Typically,the identification code employed to identify each product may be theproduct's Universal Product Code (UPC). In this way, it is possible tocollect data regarding the purchasing patterns of particular customers.

[0006] This technique, too, has several drawbacks. First, it onlycollects sales data of the particular retailer who issued the “preferredcustomer” card. It does not permit data collected by a first retailer tobe integrated and cross-referenced with data collected by otherretailers. The collected data may therefore provide a significantlyskewed perspective of a customer's purchasing patterns as a whole.

[0007] Furthermore, such systems require that the customer bring his orher card to the retailer's POS. To that end, retailers have been forcedto offer a variety of incentives, such as discounts on particular items,in order to induce customers to carry and use their “preferred customer”cards. Notwithstanding such incentives, many customers forget to bringtheir cards to the POS.

[0008] Moreover, the systems require significant hardware and softwareresources to collect and maintain the collected data. Frequently, thecustomer data is transmitted from a remote retail site to a centralcomputer maintained by the merchant. This marketing data infrastructureis often completely separate from the merchant's sales datainfrastructure and thus leads to wasteful duplicative processing of thetransaction data being collected.

SUMMARY OF THE INVENTION

[0009] The present invention overcomes the drawbacks of the prior art byproviding a system and method for efficient collection and organizationof marketing data.

[0010] In a preferred embodiment, the present invention simultaneouslycaptures at the POS all financial and non-financial data pertaining to aspecific consumer transaction. An electronic invoice is constructed fromthe captured data and transmitted to a credit authorization location viaa communication link necessarily established to transmit a creditauthorization request for the transaction. The electronic invoicecontains line item data for each item purchased as part of thetransaction. The invoice is organized around the identification numberof the payment vehicle employed by the customer to pay for thetransaction, thus linking the purchasing information contained in theinvoice to a particular consumer.

[0011] The credit authorization location receives the transmittedelectronic invoice and forwards the invoice to a data warehouse, whichmay be located in a location remote from the credit authorizationlocation. The data warehouse comprises a plurality of related datastructures for storing the received data. The related data structurespermit simple and flexible analysis and searching of the collectedmarket data.

BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The above summary of the invention will be better understood whentaken in conjunction with the following detailed description andaccompanying drawings in which:

[0013]FIG. 1 is a block diagram of a system architecture suitable forimplementing a first preferred embodiment of the present inventionwherein sales transactions are conducted via the internet.

[0014]FIG. 2 is a block diagram of a system architecture suitable forimplementing a second preferred embodiment of the present inventionwherein sales transactions are conducted at a physical POS.

[0015]FIG. 3 is a flowchart depicting the operation of the firstpreferred embodiment of the present invention.

[0016]FIG. 4 is a schematic representation of a preferred embodiment fora line item listing in an electronic invoice.

[0017]FIG. 5 is a flowchart depicting the operation of the secondpreferred embodiment of the present invention.

[0018]FIG. 6 is a block diagram of one possible structure of a datawarehouse for storing collected marketing data.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0019]FIG. 1 shows a system architecture suitable for implementing theefficient market data collection system of the present invention in aninternet purchasing environment. As shown in FIG. 1, the architecturecomprises a customer terminal 105 typically located in a customer's homeor workplace. Customer terminal 105 is provided with a modem 110. Modem110 may be an internal modem located inside customer terminal 105 or mayalternatively comprise an external modem. Customer terminal 105 mayfurther be provided with a payment vehicle scanner 107, the purpose ofwhich will be described below.

[0020] The architecture further comprises a POS location denotedgenerally as 115. POS location 115 comprises a POS computer 120 suitablefor receiving and processing orders placed with a merchant. Associatedwith POS computer 120 is an inventory database 127 which storesinformation relating to the merchant's inventory such as the types ofgoods, quantity of goods, and price of goods in the merchant'sinventory. POS computer 120 is further provided with a first modem 125and a second modem 130.

[0021] POS location 115 may further comprise a shipping departmentcomputer 135 which is linked to POS computer 120. As described in moredetail below, shipping department computer 135 receives invoices fororders placed with POS computer 120 and tracks filling and shipping ofthe order. Customer terminal 105 and POS computer 120 are adapted topermit communication therebetween via the internet. As known in the art,this connection is generally established via one or more internetgateways. Illustratively, as shown in FIG. 1, customer terminal 105 istypically connected to a first internet gateway 150 via a telephone line145. Similarly, POS computer 120 is typically connected to a secondinternet gateway 155 via telephone line 160. Gateways 150 and 155 aretypically connected via an internet backbone 140.

[0022] Gateways 150 and 155 are typically operated by internet serviceproviders who provide access to the internet for a subscription fee.Alternatively, a large merchant might own and maintain its own internetgateway. In that instance, POS computer 120 would typically be connecteddirectly to internet gateway 155 via a dedicated data line.

[0023] In other embodiments, customer computer 105 may be connected toPOS computer 120 via a direct dial connection.

[0024] The architecture of FIG. 1 further comprises a creditauthorization location 165 typically located in a location remote fromPOS location 115. Credit authorization location 165 is typically ownedand operated by the financial institution which has issued the paymentvehicle employed by the customer to pay for items purchased at the POS,as described in more detail below. Credit authorization location 165preferably comprises a credit authorization computer 170 which receivescredit authorization requests from POS computer 120, evaluates thereceived requests, and transmits to POS computer 120 an authorization ofthe transaction or a denial of the transaction depending on variousparameters such as whether the requested credit line exceeds the creditlimit of the customer.

[0025] Credit authorization computer 170 is provided with a modem 175.Typically, POS computer 120 and credit authorization computer areadapted to permit communication therebetween via telephone line 180 andmodems 130, 175. Alternatively, other transmission paths forcommunicating credit requests and authorizations may be employed.

[0026] Also shown in FIG. 1 is a data warehouse 185 which may be locatedat credit authorization location 165 or alternatively may be located ata location remote from credit authorization location 165. As describedin more detail below, data warehouse 185 stores detailed marketing dataregarding transactions occurring at points of sale such as POS 115.

[0027] Turning to FIG. 2 there is shown an alternative architecturewhich illustrates the more traditional setting wherein a customer isphysically located at the POS at the time of the transaction. As will berecognized, the architectures of the two purchasing environments sharemany common elements, and like elements in FIGS. 1 and 2 have beenlabelled with like reference numerals.

[0028] Thus, as shown in FIG. 2, the physical POS environment comprisesa POS computer 120 which has associated therewith an inventory database127 and a shipping department computer 135. Similarly, POS 120 isconnected via modem 130 and telephone line 180 to credit authorizationlocation 165.

[0029] In addition, the physical POS environment further comprises aproduct scanner 205 for scanning into POS computer 120 identificationcodes representative of the items to be purchased by the customer.Alternatively, the system may comprise a keyboard 210 or other dataentry devices 215 for scanning this information. The system is furtherprovided with a payment vehicle scanner 220 for scanning theidentification number and associated PIN of the customer's paymentvehicle into POS computer 120.

[0030] In the physical POS environment, a customer will typicallycollect in a basket or wagon the items he wishes to purchase, and bringthem to a particular location where POS terminals are located. Anemployee of the merchant uses product scanner 205 to scan a bar code orother product identifier printed on the item into POS computer 120.Alternatively, the employee may manually enter information identifyingthe items to be purchased via keyboard 210 or other data entry devices215.

[0031] Operation of a preferred embodiment of the efficient market datacollection system of the present invention in the internet purchasingenvironment will now be described in connection with FIG. 3. As shown inFIG. 3, in step 302 the customer establishes a link with POS computer120 via internet backbone 140. To establish this link, the customertypically logs onto his internet account and is provided access to theinternet via internet gateway 150. The customer then enters the webaddress of a retailer's website and is connected to the website viainternet gateway 155.

[0032] In step 304 the customer selects the items which he desires topurchase. Illustratively, the merchant's website may comprise aninterface which displays information regarding items offered for saleand may, for example, permit a customer to select items for purchase byclicking on icons or by typing in the identification number or name ofparticular items. Similarly, the interface may permit the customer toclick on or otherwise identify how many of each item he wishes topurchase.

[0033] In step 306 the customer enters the identification number of thepayment vehicle which he wishes to use to pay for the items to bepurchased. This information is typically entered in response to a promptfrom the merchant's website, and may be entered manually, oralternatively may be entered by swiping the payment vehicle throughpayment vehicle scanner 107. The payment vehicle employed by thecustomer preferably is a smart card. Alternatively, the payment vehiclemay be a magnetic stripe card such as those employed as credit cards,charge cards, or debit cards, or any other payment vehicle whichrequires verification to authorize a transaction. As known in the art,smart cards provide enhanced security over traditional magnetic stripecards because they are typically manufactured to be resistant tophysical probing by electronic instruments and physical disassembly. Inaddition, smart cards may employ symmetric or asymmetric cryptographysoftware in order to increase the security of communications between thesmart card and a merchant.

[0034] In addition to the identification number of the vehicle, paymentvehicle information generally comprises a PIN whose purpose is to ensurethat the person employing the payment vehicle is authorized to do so.

[0035] In step 308, POS computer 120 creates an electronic invoice fromthe information entered by the customer. The invoice comprises a lineitem listing concerning the items purchased by the customer. Each lineitem entry in the listing comprises the identity of a purchased item,the cost of the item, and the number purchased of the item. Typically,the identity of the item is represented by an identification code suchas a UPC number which is retrieved by POS computer from inventorydatabase 127. One illustrative arrangement for the line item listing isshown in FIG. 4. As those skilled in the art will recognize, theparticular fields shown in FIG. 4 are merely illustrative, andadditional or different fields may alternatively be employed tocustomize the line item listing for a particular environment.

[0036] As shown in FIG. 4, a typical line item listing may comprise thefollowing fields:

[0037] a date field, which stores the date on which the transactionoccurred;

[0038] a time field, which stores the time at which the transactionoccurred;

[0039] a retail location identification field, which stores a uniqueidentifier typically allocated by credit authorization location 165 toidentify the retail location submitting the line item listing;

[0040] a payment vehicle identifier, which stores the identificationnumber of the payment vehicle used by the customer to pay for thetransaction;

[0041] an invoice number field, which stores a unique identifier for theline item listing assigned by the retailer;

[0042] a total amount field, which stores the total dollar amount of thetransaction;

[0043] a number of items field, which stores the number of distinctitems purchased;

[0044] a product identifier field, which stores a unique identifier fora purchased product (typically a UPC or other standard code);

[0045] a quantity field, which stores the number of a product that waspurchased;

[0046] a unit price field, which stores the price of a purchasedproduct;

[0047] a total price field, which stores the product of the quantityfield and the unit price field for each purchased product; and

[0048] a remarks field, which stores remarks regarding the transactionthat the merchant might have.

[0049] Line item entries may also be created for other aspects of thetransaction, such as the tax, retailer discounts, etc. As illustrativelyshown in FIG. 4, such line item entries may comprise a uniquealphanumeric code that identifies the item (e.g., “T-A-X”) and is storedin the product identification field. The total amount of the item (e.g.,the tax) may be stored in the total price field.

[0050] In step 310, a program resident in POS computer 120 creates aninvoice packet for transmission to credit authorization location 165.The invoice packet comprises the line item listing described above. Theinvoice packet further comprises a request for authorization from creditauthorization location 165. The request for authorization typicallycomprises the identification number and PIN of the customer's paymentvehicle and the total amount of the sale.

[0051] In step 312, the invoice packet is transmitted to creditauthorization location 165. In the prior art, transmission from themerchant to credit authorization computer 170 served only one purpose:To request authorization for a transaction. In contrast, the purpose ofthe invoice packet of the present invention is two fold: First, torequest authorization for the transaction from credit authorizationlocation 165, and second, to transmit to credit authorization location165 a line item listing concerning the transaction. In this way, theinvention efficiently employs the communications link established withcredit authorization location 165 to simultaneously transmit thereto aline item listing comprising complete marketing data concerning thetransaction.

[0052] In decision step 314, credit authorization computer 170determines whether or not to approve the credit request received fromPOS computer 120. This determination typically comprises the step ofdetermining whether the total cost of the items listed on the invoiceexceeds the customer's credit limit. If the customer's credit limit isexceeded, then decision step 314 fails and the system proceeds to step316 wherein credit authorization computer 170 transmits a denial messageto POS computer 120 via line 180. In step 318, POS computer 120 receivesthe denial message from credit authorization computer 120 and cancelsthe transaction. The merchant may also take additional steps typicallyassociated with a denial of a request for credit authorization, as knownin the art.

[0053] If, on the other hand, the customer's credit limit is notexceeded, then decision step 314 succeeds and the system proceeds tostep 320 wherein credit authorization computer 170 transmits a creditapproval to POS computer 120 via line 180. Concurrently, in step 322credit authorization computer 170 takes additional bookkeeping actionstypically associated with approval of a financial transaction. Forexample, as known in the art, credit authorization computer 170typically updates the customer's account by debiting the customer'scredit limit in the amount of the transaction.

[0054] Upon receipt of the transaction authorization from creditauthorization location 165, in step 324, the merchant commences steps tocomplete the sale. These typically include transmitting a confirmationto the customer and preparing the order for shipping.

[0055] In step 326, credit authorization computer 170 transmits a copyof the invoice packet received from POS computer 120 to data warehouse185. As noted above, this invoice contains line item information on eachitem purchased by the customer as well the identification number of thepayment vehicle used by the customer to pay for the transaction. In step328, data warehouse 185 processes the received invoice packet and storesthe marketing data contained therein in a relational database, as willbe described in further detail below.

[0056] Thus, the present invention facilitates the collection ofdetailed line item purchasing information which is linked to aparticular customer via his payment vehicle identification number, in amanner heretofore not possible. In particular, because the paymentvehicle is employed as the central identifier for the transaction, eachitem in the line item listing is particularly identified with anindividual customer. In addition, because the line item listing istransmitted as part of an invoice packet comprising a creditauthorization request, the present invention allows efficient collectionof marketing data by permitting marketing data to be collected at acentral location without requiring an additional communication from thePOS to a central data repository.

[0057] Operation of a preferred embodiment of the efficient market datacollection system of the present invention in the physical purchasingenvironment will now be described in connection with FIG. 5.

[0058] As shown in FIG. 5, in step 502, a customer enters a retaillocation maintained by a merchant. In step 504, the customer selectsitems to be purchased and brings them to a point-of-sale terminal. Alsoin step 504, an employee of the merchant uses product scanner 205 toscan a bar code or other code printed on the item into point-of-salecomputer 120. Alternatively, the employee may manually enter informationidentifying the items to be purchased via keyboard 210 or other dataentry devices 215. In step 506, the customer identifies for the merchantthe payment vehicle to be used to pay for the selected items. Typically,the customer may hand the payment vehicle to an employee of the merchantor may alternatively swipe the payment vehicle through a payment vehiclescanner 220 located near point-of-sale computer 120.

[0059] The remainder of the steps performed in the physical-purchaseembodiment of the present invention are the same as those performed inthe on-line-purchase embodiment described above, and corresponding stepsin FIGS. 3 and 5 are identified by corresponding numerals.

[0060] The present invention also provides a novel relational storagearrangement for the collected marketing data which facilitates dataanalysis. As described below, the data are stored in a relationaldatabase designed to facilitate flexible and particularized datasearching. A schematic diagram illustrating a preferred relationaldatabase of the present invention is shown in FIG. 6.

[0061] As shown in FIG. 6, data warehouse 185 comprises a first datastructure 600 for storing the content of received electronic invoices.Data warehouse 185 creates a new record in data structure 600 for eachelectronic invoice received from credit authorization location 165. In apreferred embodiment, the record may comprise the following fields:

[0062] a retail location identification field, which stores the uniqueidentifier typically allocated by credit authorization location 165 toidentify the retail location submitting the electronic invoice;

[0063] an invoice identification field, which stores a unique identifierfor the invoice assigned by the retailer;

[0064] a payment vehicle identification field, which stores theidentification number of the payment vehicle employed by the customer topay for the transaction;

[0065] an invoice number field, which stores a unique identifier for theinvoice assigned by data warehouse 185;

[0066] a date field, which stores the date on which the transactionoccurred; and

[0067] a total amount field, which stores the total dollar amount of thetransaction.

[0068] Data warehouse 185 preferably further comprises a data structure601 for storing information regarding each line item on the receivedelectronic invoice. When an electronic invoice is received by datawarehouse 185 it creates a new record for each line item on the invoice.In a preferred embodiment, the record may comprise the following fields:

[0069] an invoice identification field, which stores the uniqueidentifier for the invoice assigned by the retailer;

[0070] a product code field, typically the UPC or other standard codefor the purchased item;

[0071] an invoice number field, which stores the unique identifier forthe invoice assigned by data warehouse 185; and

[0072] a line item total amount field, which stores the total dollaramount of the line item entry.

[0073] Data warehouse 185 further comprises a data structure 602 whichstores universal identification codes for every product stored in datawarehouse 185. The purpose of this data structure and a preferredembodiment for its design will now be described.

[0074] The UPC coding scheme cannot be used to cross reference marketingdata by category, such as by product type or class. This is because theUPC is not a hierarchical coding scheme. Instead, each UPC number as awhole identifies a particular product made by a specific manufacturer.The digits which make up the code, however, do not convey anysubstantive information regarding the class of products to which theparticular product belongs.

[0075] In contrast, the present invention preferably employs ahierarchical coding scheme in which each portion of a code identifies asignificant characteristic of the product. Thus, the structure of thecoding scheme itself conveys information about the relationship betweendifferent products stored in data warehouse 185. As noted below, thishierarchical scheme facilitates search and analysis of the collectedmarketing data stored in data warehouse 185. The particular hierarchicalscheme employed is not critical to implementation of the presentinvention.

[0076] In a preferred embodiment, the hierarchical coding scheme of thepresent invention comprises a plurality of unique universalidentification codes, called UIDCs. Each UIDC is preferably descriptiveof a particular product or service category in such a manner that thecritical characteristics of the product or service category can bedetermined by resorting to the UIDC definitions associated with thecategory's code.

[0077] Illustratively, the hierarchical system of the present inventionmight classify tennis shoes as a product category and assign to thatproduct category a unique UIDC. The hierarchical scheme might furtherclassify tennis shoes as a subcategory of athletic footwear. Athleticfootwear might itself be a subcategory of a broader categoryencompassing footwear generally, which might in turn be a subcategory ofa still broader category encompassing clothing of all varieties.

[0078] In the above illustrative example, the UIDC for tennis shoes maypreferably comprise a plurality of code segments. A first segment wouldidentify tennis shoes as belonging to the category of clothing. TheUIDCs of all product categories belonging to the clothing category wouldshare this code segment. A second segment would identify tennis shoes asbelonging to the subcategory of footwear. The UIDCs of all productcategories belonging to the footwear subcategory would share this codesegment. A third segment would identify tennis shoes as belonging to thesubcategory of athletic footwear. The UIDCs of all product categoriesbelonging to the athletic footwear subcategory would share this codesegment. A fourth segment would uniquely identify the product categoryof tennis shoes, as distinguished from other product categories in theathletic footwear family.

[0079] The present invention is not limited to the particularhierarchical coding scheme described above, and may employ any suitablehierarchical code, including those that do not comprise a plurality ofcode segments as in the above illustrative example.

[0080] Once a hierarchical coding scheme is adopted, each product orservice stored in warehouse 185 (as identified by a unique UPC number)is assigned one or more UIDCs corresponding to the product categories towhich the product or service belongs. In the above example, Nike (TM)tennis shoes and Addidas (TM) tennis shoes, each bearing distinct UPCcodes, would be assigned the same UIDC corresponding to the tennis-shoeproduct category.

[0081] In a preferred embodiment, data structure 602 contains aplurality of records, each of which stores data relating to oneuniversal identification code. Preferably, each record contains thefollowing fields:

[0082] a universal identification code field, which stores the universalidentification code for a product;

[0083] a description field, which defines the scope of products includedwithin the universal identification code; and

[0084] a keywords field, which stores a set of keywords that may be usedto facilitate the look up of unknown codes. For example, the system maybe programmed to retrieve all UIDCs associated with a particularkeyword, or group of keywords, entered by a user.

[0085] Data warehouse 185 further comprises a data structure 603 whichstores information regarding manufacturers. In a preferred embodiment,each record in data structure 603 comprises the following fields:

[0086] a manufacturer identification field, which stores a uniqueidentifier assigned to the manufacturer by data warehouse 185; and

[0087] a manufacturer information field which stores further informationrelating to the manufacturer such as its name, address, and telephonenumber.

[0088] Data warehouse 185 further comprises a data structure 604 whichstores information relating to each marketed product and links theproduct to one or more universal identification codes. As those skilledin the art will recognize, manufacturers may at times bundle togetherthe sale of two or more items, and assign to the bundled items a singleUPC number. In that instance, data structure 604 associates two or moreuniversal identification codes (one for each bundled item) with a singleUPC number, as described below. In a preferred embodiment, each recordin data structure 604 comprises the following fields:

[0089] a universal identification code field, which stores the universalidentification code for the product (or more than one universalidentification code in the case of bundled products);

[0090] a product code field, which stores the UPC number for theproduct;

[0091] a manufacturer identification field, which stores the identity ofthe manufacturer of the product;

[0092] a product name field, which stores the name assigned to theproduct by the manufacturer;

[0093] a description field, which stores a description of the product;and

[0094] a keywords field, which stores a set of key words that facilitatelooking up products. For example, the system may be programmed toretrieve all UIDCs associated with a particular keyword, or group ofkeywords, entered by a user.

[0095] Data warehouse 185 further comprises a data structure 605 whichstores information relating to customers. In a preferred embodiment,each record in data structure 605 comprises the following fields:

[0096] a customer identification field, which stores a unique identifierassigned to the customer by data warehouse 185; and

[0097] a customer information field, which stores other informationregarding the customer such as the customer's name, address, andtelephone number.

[0098] Data warehouse 185 further comprises a data structure 606 whichstores information concerning retailers. In a preferred embodiment, eachrecord in data structure 606 comprises the following fields:

[0099] a retailer identification field, which stores a unique identifierassigned to the retailer by data warehouse 185; and

[0100] a retailer information field, which stores further informationrelating to the retailer such as the retailer's name, address, andtelephone number.

[0101] Data warehouse 185 further comprises a data structure 607 whichcomprises a Geographical Information System (GIS). As known in the art,a GIS comprises a set of tables that link groups of customers on thebasis of distinct parameters, including: residence, age, ethnicity,family status, phone numbers, taxes, vocation, number of credit cardsheld, etc. Data structure 607 facilitates analysis of the marketing datastored in data warehouse 185 across segments of the population, asdescribed below. For example, using the linking tables of data structure607, the system may generate a list of all households in the southwestUnited States with four or more members and a household income of atleast $45,000/yr., in which one or more members of the household isemployed by an insurance company.

[0102] Data warehouse 185 further comprises a data structure 608 whichlinks particular payment vehicles to particular individuals. In apreferred embodiment, each record in data structure 608 comprises thefollowing fields:

[0103] a vehicle identification number, which stores the identificationnumber of a payment vehicle; and

[0104] a customer identification number, which stores the identificationnumber of a customer associated with the payment vehicle.

[0105] Data warehouse 185 further comprises a data structure 609 whichlinks particular retailing locations to particular retail companies,since each retailer may maintain more than one retail location. In apreferred embodiment, each record in data structure 609 preferablycomprises the following fields:

[0106] a retailer identification field, which stores the identificationnumber of the retailer which maintains the retail location; and

[0107] a retail location identification field, which stores the uniqueidentifier typically allocated by credit authorization location 165 toidentify a retail location.

[0108] The data structures described above permit data warehouse 185 tobe flexibly searched using a wide assortment of search queries. Thispermits particularized market data satisfying any specific constraint orcombination of constraints on the values of the fields in datastructures 600-609 to be retrieved from data warehouse 185.Illustratively, a user would be able to determine:

[0109] (1) total volume of sales of tennis shoes (UIDC 123-456-789) overthe past 24 months, grouped by month and state.

[0110] (2) the percentage of athletic footwear sold in the last yearthat was manufactured by Nike (TM).

[0111] (3) the name and address of every person who purchased footwearfrom Addidas (TM) and at least one other company in the past year.

[0112] (4) line item details of every purchase made by John Q. Doe usingpayment vehicle Master Card (TM) 1234 5678 9012 3456 during the periodJun. 6, 1997 to Jul. 23, 1997.

[0113] (5) a list of every American Express (TM) cardholder who haspurchased within the last three weeks a combination of running shoes,running shorts, and running socks in a premium price range.

[0114] (6) total sales volume of bicycle helmets in a defined pricerange.

[0115] (7) total sales volume by brand of all power tools purchased inthe last six months.

[0116] Those skilled in the art will understand how to program a generalpurpose computer to interactively query data warehouse 185 in order toobtain responses to the above queries, and others. As those skilled inthe art will recognize, the system of the present invention facilitatessuch searches in several specific ways. By way of example and notlimitation, the hierarchical coding scheme of the present inventionpermits the system to search the collected marketing data at manyconceptual levels. As noted above, for example, the UIDC for aparticular product category (e.g., tennis shoes) may identify theproduct category as belonging to a progression of hierarchicallyrelated, successively broader, categories. This permits the system tomore easily respond to queries of varying breadth, ranging from narrowqueries concerning a single product or service category to broaderqueries concerning classes of related product and service categories.

[0117] It should be recognized that specific queries to data warehouse185 may be restricted by law or for other reasons. For example,accessing customer-specific purchasing information might be prohibitedby law in some states. Similarly, credit authorization location 165might contractually obligate data warehouse 185 to limitcustomer-specific queries for reasons of public relations or to stopcustomers from abandoning payment vehicles issued by the creditauthorization institution.

[0118] While the invention has been described in conjunction withspecific embodiments, it is evident that numerous alternatives,modifications, and variations will be apparent to those skilled in theart in light of the foregoing description.

1. A method of collecting marketing information, comprising: collecting,at a point-of-sale, line item data pertaining to one or moretransactions; establishing a communication link between thepoint-of-sale and a credit authorization location; transmitting a creditauthorization request from the point-of-sale to the credit authorizationlocation via the communication link; transmitting the line item datafrom the point-of-sale to the credit authorization location via thecommunication link.
 2. The method of claim 1 wherein the point-of-saleis an internet website.
 3. The method of claim 1 wherein the line itemdata comprises a UPC number for each line item, the method furthercomprising: storing the line item data transmitted from thepoint-of-sale at a location remote from the point-of-sale; identifying aproduct or service category identifier for each line item on the basisof the item's UPC number; storing each product or service categoryidentifier in linked association with the line item for which it wasidentified.
 4. A system for organizing marketing data, comprising: apoint-of-sale computer; a credit authorization computer; acommunications link linking the point-of-sale computer and the creditauthorization computer; a data storage connected to the creditauthorization computer; a database resident in the data storage andcomprising a plurality of data structures; wherein at least one of thedata structures stores line item information pertaining to one or moretransactions executed by the point-of-sale computer and reported to thecredit authorization computer; and at least a second one of the datastructures stores information indicative of the payment vehicle used topay for the transaction; the payment vehicle information for thetransaction being linked to the line item information for thetransaction.
 5. The system of claim 4 wherein the data storage islocated remote from the credit authorization computer.